Flow Actions Overview
3 minute read
Beginner
There are several types of actions available in Glific. You can select it from the node dropdown in the Flow Configure page to select the desired action type.
- Send contact a message - It sends the message to the contact in the flow. You can also add variables in the content of the message to publish the value in the message. Refer Flow level & Contact level variables to know more about how to use variables in flow.
2 . Wait for contact to respond - Get an input from contact and use it in your flow. Many option available for response type. Input send by contact will be saved in the variable under Result Name field. For more details refer Contact response type
3 . Wait for time - Send a message after a specified time gap. If the wait time is not selected, then it will put a gap of 5 seconds by default.
4 . Send a staff member a message - Send a message to staff member (other than the contact with whom current flow communication is in process) in the flow. For details refer Send message to a staff member
5 . Label the incoming message - To label the message received in the flow. This helps you generate data point and generate analytics. Ex. if someone chooses English as their preferred language you can label their message English and then generate chart for how many people selected English.
6 . Add the contact to a Collection - To add the contact (who is communicating in the flow) in a Collection already created.
7 . Remove the contact from a Collection - To remove any contact from a Collection.
8 . Update the contact - To save the contact details in the DB.
9 . Call a Webhook - To send or receive data to a 3rd party web application. Refer How to use Webhooks in Glific to know more about how to use a webhook in Glific.
10 . Enter another flow - to call another flow with in a flow.
11 . Split by custom expression - To take a decision in a flow based on the response submitted by contact.
12 . Split by a result in the flow - To take a design in the flow based on the result of user response.
13 . Split by collection membership. - This node is used to identify if the contact is a member of a particular collection. In the below example, it is checking if the contact is a member of the English collection.
14 . Split by contact field. - This node is used to make a decision in the flow based on the value of a contact variable.
15 . Wait for result - This node is used to get results from webhook results. If there is a delay in the response from webhook, then it will wait to get the result according to the time set in wait for result. Earlier, the flow used to break if there was a delay in the response from the webhook. But now, it will not break and will wait for the result from the webhook. Resume flow API is used to make this feature, which will queue the request. If there is no webhook, then wait for result will work as wait for time
16 . Start Somebody else in the flow - This node is used to start interacting with new user or a collection in the middle of the flow.
17 . Open Ticket - This node is used to ask questions and assign them to the appropriate project team member. It simplifies the process of posting queries and directing them to the right person.
To more about action types, you can refer to this article published by the Nyaruka Team. We thank the Nyaruka team for publishing it for the community.